Repository navigation
Release Python SDK 2.19.1: replay clock closed during garbage collection - #345
Merged
Merged
Conversation
Release the fix that keeps the replay clock closed to code run by cyclic garbage collection (#343, #344). Retarget the installed retry-cap qualification cell to the 2.19.1 candidate. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Member
Author
|
Candidate review. Build-only run 44360890938 (attempt 1) built head
🤖 Generated with Claude Code |
|
This was referenced Nov 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Prepares the Python SDK 2.19.1 patch release from current
main(59dda1f0, which includes #344). Not tagged or published.What ships (since 2.19.0)
ReplayClockUnavailable, and recorded history is unchanged.This PR changes the version metadata, names the CHANGELOG section
[2.19.1], and retargets the installed retry-cap cell to the 2.19.1 candidate. The Server tuple stays native 3.13.0.Locally, on Python 3.10 in a capped container:
ruff check .passes, and release metadata, the retry-cap tests,test_business_replay_clockand the replay regression corpus pass (246 passed).Remaining steps (same as 2.19.0, #342)
.github/release-candidates/2.19.1.json.ci.ymlrun withactivity_retry_cap=true,retry_cap_artifact_source=candidate.--match-head-commit).2.19.1, which triggerspublish.yml. Then verify PyPI and run the registryci.ymlrepeat onmain.🤖 Generated with Claude Code